-
Notifications
You must be signed in to change notification settings - Fork 1.1k
chore: document GitHub issues flow #67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: document GitHub issues flow #67
Conversation
536a1a4
to
1c81066
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is fantastic! Do you think you could also update .github/ISSUE_TEMPLATE.md
to help set expectations as well? I think people will probably be surprised when we close their issue, so it'd probably be helpful to include a note in the template.
Thanks!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why don't we just copy the policies right in the template. Much more likely that folks will read it.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Woo!
🎉 This PR is included in version 2.4.0 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
…ing-library#67) * feat(queries): allow overriding queries in getQueriesForElement * feat(queries): remove array option
What:
Why:
https://twitter.com/samselikoff/status/991395669016436736
One difference I'm proposing is not closing new feature requests to make it easier to use the GitHub UI to sort/filter/browse open requests. But closing issues and adding a "votes needed" is a valid idea, too.
How:
Checklist: